Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 167d4617dadd7dc4893e6f4db033523b709f2f44d1e1335f463bd811396cfc28

Tx prefix hash: 50dfed19f49c57466da05801e40c78e1738ffdf5e299e1f8ca475a418bec6c69
Tx public key: 6ef1e3123192f02df652754d18a70e95970665f430b56959e1a441625da6b3b8
Timestamp: 1730360473 Timestamp [UCT]: 2024-10-31 07:41:13 Age [y:d:h:m:s]: 00:000:14:04:44
Block: 1143376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414 RingCT/type: yes/0
Extra: 016ef1e3123192f02df652754d18a70e95970665f430b56959e1a441625da6b3b80211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41b0fb7d8921a604e6be69e56de599caa6ba4b3ee4e90b36f54224b0d82bb9ea 0.600000000000 1627241 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": 1143386, "vin": [ { "gen": { "height": 1143376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41b0fb7d8921a604e6be69e56de599caa6ba4b3ee4e90b36f54224b0d82bb9ea" } } ], "extra": [ 1, 110, 241, 227, 18, 49, 146, 240, 45, 246, 82, 117, 77, 24, 167, 14, 149, 151, 6, 101, 244, 48, 181, 105, 89, 225, 164, 65, 98, 93, 166, 179, 184, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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