Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9946eeaecdbeb001b468cf76ef9067d4b21d0a68f29b84be3cbd966b8e5e5884

Tx prefix hash: 6d49b7e75e7edc8efcc96d89979f44e9be988f2934c0e118ad1c9bc2994f3e7e
Tx public key: ffd4280e4a59e62e4b29e1fb682a0536d53426da67cec38ba971d69a7c83e938
Timestamp: 1745723623 Timestamp [UCT]: 2025-04-27 03:13:43 Age [y:d:h:m:s]: 00:207:22:19:53
Block: 1270304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146312 RingCT/type: yes/0
Extra: 01ffd4280e4a59e62e4b29e1fb682a0536d53426da67cec38ba971d69a7c83e93802110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc00c49c1f2cd546179a1ab957dce8954b31e2eb75fa0a082e81446b2225ad14 0.600000000000 1757545 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": 1270314, "vin": [ { "gen": { "height": 1270304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc00c49c1f2cd546179a1ab957dce8954b31e2eb75fa0a082e81446b2225ad14" } } ], "extra": [ 1, 255, 212, 40, 14, 74, 89, 230, 46, 75, 41, 225, 251, 104, 42, 5, 54, 213, 52, 38, 218, 103, 206, 195, 139, 169, 113, 214, 154, 124, 131, 233, 56, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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