Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d944a11896a650e8eba2a62d69c016d1a02f620513060474c0d746f0ebf52c4c

Tx prefix hash: 3ead6b3ef50f0076c4f800977802361e21a793e1c2ccf512abef02d919e5dcaa
Tx public key: 4452c27266bbecaf781e983b3fcf00a4a31251f8bc82b5d1f14b70b239d9a729
Timestamp: 1577511516 Timestamp [UCT]: 2019-12-28 05:38:36 Age [y:d:h:m:s]: 05:067:23:54:58
Block: 33214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1198523 RingCT/type: yes/0
Extra: 014452c27266bbecaf781e983b3fcf00a4a31251f8bc82b5d1f14b70b239d9a7290211000000038a2ee0d9000000000000000000

1 output(s) for total of 476.375138218000 dcy

stealth address amount amount idx
00: 56d74c513a577b30924144ef13a1e7200403a64bff2f93dc3d37add1a0196741 476.375138218000 55551 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": 33224, "vin": [ { "gen": { "height": 33214 } } ], "vout": [ { "amount": 476375138218, "target": { "key": "56d74c513a577b30924144ef13a1e7200403a64bff2f93dc3d37add1a0196741" } } ], "extra": [ 1, 68, 82, 194, 114, 102, 187, 236, 175, 120, 30, 152, 59, 63, 207, 0, 164, 163, 18, 81, 248, 188, 130, 181, 209, 241, 75, 112, 178, 57, 217, 167, 41, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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