Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9387d34a3d15bbcf3263bee74328b4e30d4007ba23a5371de43d3fa5fb16795

Tx prefix hash: 3f1d0625a96922605db156d489e0ccf27c98c3a28fc6eeb4a1ccdca6aa6b8b87
Tx public key: ae1758b81359a59125111c41b7fb2aaa9db84b9d3a51e14119d9466611c3de6a
Timestamp: 1711674598 Timestamp [UCT]: 2024-03-29 01:09:58 Age [y:d:h:m:s]: 01:047:15:25:23
Block: 988556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295016 RingCT/type: yes/0
Extra: 01ae1758b81359a59125111c41b7fb2aaa9db84b9d3a51e14119d9466611c3de6a02110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 446f18875791aea16bd3f14aab38dcde2843331d5145ccb1a2a427c99e03b8e2 0.600000000000 1448835 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": 988566, "vin": [ { "gen": { "height": 988556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "446f18875791aea16bd3f14aab38dcde2843331d5145ccb1a2a427c99e03b8e2" } } ], "extra": [ 1, 174, 23, 88, 184, 19, 89, 165, 145, 37, 17, 28, 65, 183, 251, 42, 170, 157, 184, 75, 157, 58, 81, 225, 65, 25, 217, 70, 102, 17, 195, 222, 106, 2, 17, 0, 0, 0, 15, 89, 218, 211, 245, 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