Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e37d0c03bd99b93acee8cfe876804ff62f198ef1341756a190593918f41183

Tx prefix hash: 455fc1744a9feae8c053714bd1d67e9675ba611df617fd9c145e72650ac35a4e
Tx public key: 7d48d746e24edb4e32433f8c757fa06ad94aacffe53050bb5dc64d1bcfd4dcd6
Timestamp: 1722339688 Timestamp [UCT]: 2024-07-30 11:41:28 Age [y:d:h:m:s]: 00:247:11:40:37
Block: 1076957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176772 RingCT/type: yes/0
Extra: 017d48d746e24edb4e32433f8c757fa06ad94aacffe53050bb5dc64d1bcfd4dcd602110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b3510353030a8e9c36b36e1d751babbe60dd5e70fda74f5d46797b2c00b7e6c 0.600000000000 1549500 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": 1076967, "vin": [ { "gen": { "height": 1076957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b3510353030a8e9c36b36e1d751babbe60dd5e70fda74f5d46797b2c00b7e6c" } } ], "extra": [ 1, 125, 72, 215, 70, 226, 78, 219, 78, 50, 67, 63, 140, 117, 127, 160, 106, 217, 74, 172, 255, 229, 48, 80, 187, 93, 198, 77, 27, 207, 212, 220, 214, 2, 17, 0, 0, 0, 17, 145, 225, 60, 4, 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