Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ec047091783f097a9bc02e2f6800cc9082373eabd5a84763af30dfdf789319

Tx prefix hash: fb4ab40a9bcbb9eb6b79db35a149540b437bc4068be311ea02ac8aedef454df9
Tx public key: a69f467c300a0b1b1a2e299ba9f9002d98e89d05c2272255bb6d522761e6c591
Timestamp: 1699447272 Timestamp [UCT]: 2023-11-08 12:41:12 Age [y:d:h:m:s]: 01:074:00:15:10
Block: 887174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314253 RingCT/type: yes/0
Extra: 01a69f467c300a0b1b1a2e299ba9f9002d98e89d05c2272255bb6d522761e6c591021100000003faf35c9c000000000000000000

1 output(s) for total of 0.705381811000 dcy

stealth address amount amount idx
00: 16e11d8b93372b33215cbf18360658bbc81101ef96e24e8fadc1946176590053 0.705381811000 1343031 of 0

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": 887184, "vin": [ { "gen": { "height": 887174 } } ], "vout": [ { "amount": 705381811, "target": { "key": "16e11d8b93372b33215cbf18360658bbc81101ef96e24e8fadc1946176590053" } } ], "extra": [ 1, 166, 159, 70, 124, 48, 10, 11, 27, 26, 46, 41, 155, 169, 249, 0, 45, 152, 232, 157, 5, 194, 39, 34, 85, 187, 109, 82, 39, 97, 230, 197, 145, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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