Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4089c86b7ed6b095712f9956a31bd9772f069002e5486d425baa367904c8e68c

Tx prefix hash: a1ad37a180b9e9a709126f7ca7b9b6199f5fe93035d091af2fc7b42928c9a654
Tx public key: 138e1162e506704d841663d4822da8314f50f555e57bf965f8fe07623330e81e
Timestamp: 1613171587 Timestamp [UCT]: 2021-02-12 23:13:07 Age [y:d:h:m:s]: 03:329:16:34:09
Block: 197619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 994645 RingCT/type: yes/0
Extra: 01138e1162e506704d841663d4822da8314f50f555e57bf965f8fe07623330e81e02110000017557f0ba47000000000000000000

1 output(s) for total of 135.898403289000 dcy

stealth address amount amount idx
00: ac0e67d729c642c3314a97b196d8043fd432e2529d0584bd6d7c374b77c0f28a 135.898403289000 404299 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": 197629, "vin": [ { "gen": { "height": 197619 } } ], "vout": [ { "amount": 135898403289, "target": { "key": "ac0e67d729c642c3314a97b196d8043fd432e2529d0584bd6d7c374b77c0f28a" } } ], "extra": [ 1, 19, 142, 17, 98, 229, 6, 112, 77, 132, 22, 99, 212, 130, 45, 168, 49, 79, 80, 245, 85, 229, 123, 249, 101, 248, 254, 7, 98, 51, 48, 232, 30, 2, 17, 0, 0, 1, 117, 87, 240, 186, 71, 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