Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233d0eaba6350f9216eb1919ea931c5ebd9ea1286aea078db039297ff2601f49

Tx prefix hash: bfe41bfd63c65f066881c9a6909038d59a182078e82ea00b6e1f062d85ddb182
Tx public key: 4ee4d7572d7738d330ac28b6f5a9f19356942b3d5335ef9b21ded4a9068fc2a5
Timestamp: 1577141818 Timestamp [UCT]: 2019-12-23 22:56:58 Age [y:d:h:m:s]: 05:082:05:10:46
Block: 30164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1208709 RingCT/type: yes/0
Extra: 014ee4d7572d7738d330ac28b6f5a9f19356942b3d5335ef9b21ded4a9068fc2a5021100000015e39b962a000000000000000000

1 output(s) for total of 487.590245084000 dcy

stealth address amount amount idx
00: 9e14e3498418c276bab9224523e736d72a9fa818a953e79858231f84a0eec748 487.590245084000 49806 of 0

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": 30174, "vin": [ { "gen": { "height": 30164 } } ], "vout": [ { "amount": 487590245084, "target": { "key": "9e14e3498418c276bab9224523e736d72a9fa818a953e79858231f84a0eec748" } } ], "extra": [ 1, 78, 228, 215, 87, 45, 119, 56, 211, 48, 172, 40, 182, 245, 169, 241, 147, 86, 148, 43, 61, 83, 53, 239, 155, 33, 222, 212, 169, 6, 143, 194, 165, 2, 17, 0, 0, 0, 21, 227, 155, 150, 42, 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