Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6658f2e48252571befba4a4ce49ad89e568d62b3aefe48f7af59bd841f0f0616

Tx prefix hash: 2ee46b360dc85b3b54960c965d0b54d52873dc01b74a4ffa8add8e2eb7bf87a2
Tx public key: ef446851d64c5b8180774ee5b1a892e156c3013638ca1f2fb2bb1da6a7085eca
Timestamp: 1709204901 Timestamp [UCT]: 2024-02-29 11:08:21 Age [y:d:h:m:s]: 01:077:12:19:00
Block: 968065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316425 RingCT/type: yes/0
Extra: 01ef446851d64c5b8180774ee5b1a892e156c3013638ca1f2fb2bb1da6a7085eca02110000000349a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48bb8c77bb6d80a58c49407d0a3c58e9d5f008d59b2c06d936f8524ff552a372 0.600000000000 1427862 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": 968075, "vin": [ { "gen": { "height": 968065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48bb8c77bb6d80a58c49407d0a3c58e9d5f008d59b2c06d936f8524ff552a372" } } ], "extra": [ 1, 239, 68, 104, 81, 214, 76, 91, 129, 128, 119, 78, 229, 177, 168, 146, 225, 86, 195, 1, 54, 56, 202, 31, 47, 178, 187, 29, 166, 167, 8, 94, 202, 2, 17, 0, 0, 0, 3, 73, 161, 133, 187, 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