Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1b45f31bff6038d916aac4c4a03bb8ab4cac4142fcea6f78c5045752dc153b

Tx prefix hash: db3e66fbd0cd7dd192693a4a1234531c84ef2587b4989046be770d1ff14cd201
Tx public key: 3caa39b70632d586453d6d03854712c62a0837d7dc9507e31c5a6b89ee8bcd5e
Timestamp: 1716008049 Timestamp [UCT]: 2024-05-18 04:54:09 Age [y:d:h:m:s]: 00:179:06:24:19
Block: 1024459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128319 RingCT/type: yes/0
Extra: 013caa39b70632d586453d6d03854712c62a0837d7dc9507e31c5a6b89ee8bcd5e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1bdd198c3e314e657c5909bd1de5eb4cad14f5ab4199ebfe4bd803e2f5a59bf 0.600000000000 1490224 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": 1024469, "vin": [ { "gen": { "height": 1024459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1bdd198c3e314e657c5909bd1de5eb4cad14f5ab4199ebfe4bd803e2f5a59bf" } } ], "extra": [ 1, 60, 170, 57, 183, 6, 50, 213, 134, 69, 61, 109, 3, 133, 71, 18, 198, 42, 8, 55, 215, 220, 149, 7, 227, 28, 90, 107, 137, 238, 139, 205, 94, 2, 17, 0, 0, 0, 1, 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