Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4ddaab24cd899b6b09495de480c6b4aa67e981aebdd6792eade5436624f72a2

Tx prefix hash: 848742ca418f40d7af880b497e3537e9be093ec5d8b3b005d5be7692a2987af4
Tx public key: ec6230ebdbdddf2d53a3b56fd52f3ee39822f15b4069e82c6d35f54d66d893c5
Timestamp: 1732312654 Timestamp [UCT]: 2024-11-22 21:57:34 Age [y:d:h:m:s]: 00:206:00:41:12
Block: 1159535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147005 RingCT/type: yes/0
Extra: 01ec6230ebdbdddf2d53a3b56fd52f3ee39822f15b4069e82c6d35f54d66d893c5021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0ce3087487d902c68bedbaa6b51b7597d2db3725447d5a2bfac7a8a2c1b3f81 0.600000000000 1645172 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": 1159545, "vin": [ { "gen": { "height": 1159535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0ce3087487d902c68bedbaa6b51b7597d2db3725447d5a2bfac7a8a2c1b3f81" } } ], "extra": [ 1, 236, 98, 48, 235, 219, 221, 223, 45, 83, 163, 181, 111, 213, 47, 62, 227, 152, 34, 241, 91, 64, 105, 232, 44, 109, 53, 245, 77, 102, 216, 147, 197, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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