Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b810fc5f90d6cc5eb17ab890fe38fac33f087613c9ec8b69c8dcfc7db9a4eb8

Tx prefix hash: ff4d45b5336fdeb9c7403070758ea4655fd2eabb5ff3f25b59a4c0728e925442
Tx public key: a452feafb79e6eb4099c4bc7faec0f65788844df393d76a4366a75d16a01946e
Timestamp: 1731693690 Timestamp [UCT]: 2024-11-15 18:01:30 Age [y:d:h:m:s]: 00:358:19:29:10
Block: 1154397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253998 RingCT/type: yes/0
Extra: 01a452feafb79e6eb4099c4bc7faec0f65788844df393d76a4366a75d16a01946e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6f6dc389a73da6ede55d0c1f789fb47ca549d0bb417c5e901c9b70407a75fb1 0.600000000000 1640008 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": 1154407, "vin": [ { "gen": { "height": 1154397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6f6dc389a73da6ede55d0c1f789fb47ca549d0bb417c5e901c9b70407a75fb1" } } ], "extra": [ 1, 164, 82, 254, 175, 183, 158, 110, 180, 9, 156, 75, 199, 250, 236, 15, 101, 120, 136, 68, 223, 57, 61, 118, 164, 54, 106, 117, 209, 106, 1, 148, 110, 2, 17, 0, 0, 0, 3, 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