Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ca0f326b51d81a2bdbfb28b6c45fe123fb641f92e812bd45eab68f920b5a321

Tx prefix hash: 9a4b4eb9a7445ff25113abcdc955f6763d766516ffd8af9093df6c428ff573f9
Tx public key: ec5c20ff11d753d5fb1fef09d7eae4612791c91abb6904ab0d8003f5883bd58a
Timestamp: 1703590221 Timestamp [UCT]: 2023-12-26 11:30:21 Age [y:d:h:m:s]: 01:176:15:07:58
Block: 921513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387256 RingCT/type: yes/0
Extra: 01ec5c20ff11d753d5fb1fef09d7eae4612791c91abb6904ab0d8003f5883bd58a02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e6a7a956fe341c64d31c65ccc2c927bc674c1554a0abba15d6b5f13623450ee 0.600000000000 1379201 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": 921523, "vin": [ { "gen": { "height": 921513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e6a7a956fe341c64d31c65ccc2c927bc674c1554a0abba15d6b5f13623450ee" } } ], "extra": [ 1, 236, 92, 32, 255, 17, 215, 83, 213, 251, 31, 239, 9, 215, 234, 228, 97, 39, 145, 201, 26, 187, 105, 4, 171, 13, 128, 3, 245, 136, 59, 213, 138, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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