Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b911be69f8fa65d4f94f6efcf99e6f28a877f9ba8ffc9b1092137ccb644e8f92

Tx prefix hash: 8a184f8cd5c201eb11d3bbb2dc571ee40465824f2b00a0fa6d1e44b84a340fd4
Tx public key: 07c9a6330028ead7bb3c390bcfb4a189d3230d44f72e30d8aeb00a857bbf1545
Timestamp: 1714264927 Timestamp [UCT]: 2024-04-28 00:42:07 Age [y:d:h:m:s]: 00:322:16:38:46
Block: 1010003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230696 RingCT/type: yes/0
Extra: 0107c9a6330028ead7bb3c390bcfb4a189d3230d44f72e30d8aeb00a857bbf15450211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b2440f75567d93b4bfd7a02953890cf15732e6dccf807dbeb13aca873148a39 0.600000000000 1471833 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": 1010013, "vin": [ { "gen": { "height": 1010003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b2440f75567d93b4bfd7a02953890cf15732e6dccf807dbeb13aca873148a39" } } ], "extra": [ 1, 7, 201, 166, 51, 0, 40, 234, 215, 187, 60, 57, 11, 207, 180, 161, 137, 211, 35, 13, 68, 247, 46, 48, 216, 174, 176, 10, 133, 123, 191, 21, 69, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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