Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0546f359415f4d9f2b8185fbe66f1c984d993f431f476147f9a99d8dc1cfece9

Tx prefix hash: 4516b69e633cfd900f13d190750cb67c28d5cf63eb0f9c8d1cdf7e7810578532
Tx public key: 357fbdd5e9574fc00b61f575f6c41ae7d4256f01bb08d29f020bc53a0aa664ba
Timestamp: 1718790657 Timestamp [UCT]: 2024-06-19 09:50:57 Age [y:d:h:m:s]: 00:166:00:43:41
Block: 1047533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118826 RingCT/type: yes/0
Extra: 01357fbdd5e9574fc00b61f575f6c41ae7d4256f01bb08d29f020bc53a0aa664ba0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 476ac3b3f691443fae510a0cfc96442dd74d9dc141a291efd7438d8034d50292 0.600000000000 1517384 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": 1047543, "vin": [ { "gen": { "height": 1047533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "476ac3b3f691443fae510a0cfc96442dd74d9dc141a291efd7438d8034d50292" } } ], "extra": [ 1, 53, 127, 189, 213, 233, 87, 79, 192, 11, 97, 245, 117, 246, 196, 26, 231, 212, 37, 111, 1, 187, 8, 210, 159, 2, 11, 197, 58, 10, 166, 100, 186, 2, 17, 0, 0, 0, 3, 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