Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9dce39fda845849633c7de656b393cc9d3ec877a13aef69073c87ca6569a5b83

Tx prefix hash: 1ef3707bb827cd7f5a85461876e3f6f0057dc8c5da57f1575e78792e608e5b99
Tx public key: e581d86ebc631deba86421d53ed764256a941182719dcef44715a9fd1d77c2ab
Timestamp: 1745897866 Timestamp [UCT]: 2025-04-29 03:37:46 Age [y:d:h:m:s]: 00:206:12:17:52
Block: 1271749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145294 RingCT/type: yes/0
Extra: 01e581d86ebc631deba86421d53ed764256a941182719dcef44715a9fd1d77c2ab02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bd1d4a791adddfb2c59b53dc0d7bb5fc8eb11f6b8f3c488de56a8b0745ae467 0.600000000000 1759016 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1271759, "vin": [ { "gen": { "height": 1271749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bd1d4a791adddfb2c59b53dc0d7bb5fc8eb11f6b8f3c488de56a8b0745ae467" } } ], "extra": [ 1, 229, 129, 216, 110, 188, 99, 29, 235, 168, 100, 33, 213, 62, 215, 100, 37, 106, 148, 17, 130, 113, 157, 206, 244, 71, 21, 169, 253, 29, 119, 194, 171, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8