Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f6f2afe93f1bf4b4de71687dd8fb44266577cf55aa02ce898d45b0d58d2a3d4

Tx prefix hash: bdd21bf5793371b72685f2a58c63fde8594296f304c8507e38e5159484375d8b
Tx public key: 8d8ad7f7c7d176900d42e3e582f3ce96e0dcaa961397f1c8d776c718f9917ca4
Timestamp: 1726930028 Timestamp [UCT]: 2024-09-21 14:47:08 Age [y:d:h:m:s]: 00:104:20:47:39
Block: 1115015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74986 RingCT/type: yes/0
Extra: 018d8ad7f7c7d176900d42e3e582f3ce96e0dcaa961397f1c8d776c718f9917ca402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7974e67021028555d8972b917fe49402cf16576f6b758c69d2e543a9833ab6f4 0.600000000000 1594996 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": 1115025, "vin": [ { "gen": { "height": 1115015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7974e67021028555d8972b917fe49402cf16576f6b758c69d2e543a9833ab6f4" } } ], "extra": [ 1, 141, 138, 215, 247, 199, 209, 118, 144, 13, 66, 227, 229, 130, 243, 206, 150, 224, 220, 170, 150, 19, 151, 241, 200, 215, 118, 199, 24, 249, 145, 124, 164, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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