Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfd13c17f4eea3b83e26cad65674fa4d67442ff4bdee3107b3683b5feb52c65d

Tx prefix hash: d46024c6312bf76f4ac17210d1e0b392765ea6ee0c59df5eb48c019ee0d3f749
Tx public key: 392d7a0f0e6ead76c3f78acdb55de3a8e27a5a4461ead576c891c9bb8b7f861e
Timestamp: 1704077595 Timestamp [UCT]: 2024-01-01 02:53:15 Age [y:d:h:m:s]: 01:313:16:53:56
Block: 925544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483043 RingCT/type: yes/0
Extra: 01392d7a0f0e6ead76c3f78acdb55de3a8e27a5a4461ead576c891c9bb8b7f861e021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab78505742738c786c0b7fefd9b08a302101b8f01566daf8cc11228e7b066efa 0.600000000000 1383308 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": 925554, "vin": [ { "gen": { "height": 925544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab78505742738c786c0b7fefd9b08a302101b8f01566daf8cc11228e7b066efa" } } ], "extra": [ 1, 57, 45, 122, 15, 14, 110, 173, 118, 195, 247, 138, 205, 181, 93, 227, 168, 226, 122, 90, 68, 97, 234, 213, 118, 200, 145, 201, 187, 139, 127, 134, 30, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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