Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3910270c0855ccbde92891d020814d6c468d61f227e158ade033967f63302f

Tx prefix hash: abfccaa9e8ac411f1e445fd5976c49af86af9b44f4dbc2198de36734690adf20
Tx public key: cfd4e7100d341674854185b21480082238d3fb3a2e64e17f21e560b861dc7e8e
Timestamp: 1735701799 Timestamp [UCT]: 2025-01-01 03:23:19 Age [y:d:h:m:s]: 00:092:05:37:32
Block: 1187598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65699 RingCT/type: yes/0
Extra: 01cfd4e7100d341674854185b21480082238d3fb3a2e64e17f21e560b861dc7e8e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad976eb706f159d7e619e72cc1decc351228fd10b74e40e7f8168d1d7f193a42 0.600000000000 1674091 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": 1187608, "vin": [ { "gen": { "height": 1187598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad976eb706f159d7e619e72cc1decc351228fd10b74e40e7f8168d1d7f193a42" } } ], "extra": [ 1, 207, 212, 231, 16, 13, 52, 22, 116, 133, 65, 133, 178, 20, 128, 8, 34, 56, 211, 251, 58, 46, 100, 225, 127, 33, 229, 96, 184, 97, 220, 126, 142, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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