Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19c709338354fa4be9f92c322b475b3bdc8af375cce20f60ce41c1061bf85af0

Tx prefix hash: cd8c00d0555f00e2b2a34d7759ecee21ba23a2755e6caad303f36b91cda7cddc
Tx public key: f9f110e4598a9efba5b3c3002ebcf820eed3cbfe88524aa90215fc8d745b8765
Timestamp: 1730410076 Timestamp [UCT]: 2024-10-31 21:27:56 Age [y:d:h:m:s]: 00:133:12:17:29
Block: 1143779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95262 RingCT/type: yes/0
Extra: 01f9f110e4598a9efba5b3c3002ebcf820eed3cbfe88524aa90215fc8d745b8765021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc46281b1470d4372c4eda5f03919ea88e8e6e5ee96aa7d0da9374ac33ec1b2e 0.600000000000 1627768 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": 1143789, "vin": [ { "gen": { "height": 1143779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc46281b1470d4372c4eda5f03919ea88e8e6e5ee96aa7d0da9374ac33ec1b2e" } } ], "extra": [ 1, 249, 241, 16, 228, 89, 138, 158, 251, 165, 179, 195, 0, 46, 188, 248, 32, 238, 211, 203, 254, 136, 82, 74, 169, 2, 21, 252, 141, 116, 91, 135, 101, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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