Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00987a5a2e2412323dd224c16f99caf7b4d5e1e5dd387eb5d02541fd426a0e38

Tx prefix hash: e3b0c9ff9998fb774ece20b0fbbe9caa25e7a4255ac0d87bf7dbf0ddcc3978bf
Tx public key: 4a53a6d099c2e9085dc263f6d75fbd854a07f1a5c395d6e949270126ea58a60d
Timestamp: 1648495305 Timestamp [UCT]: 2022-03-28 19:21:45 Age [y:d:h:m:s]: 03:217:21:10:00
Block: 468390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933661 RingCT/type: yes/0
Extra: 014a53a6d099c2e9085dc263f6d75fbd854a07f1a5c395d6e949270126ea58a60d021100000002cb8520c2000000000000000000

1 output(s) for total of 17.219865061000 dcy

stealth address amount amount idx
00: 009fed5a7048027ec1f2cfebe647fe9bf9ad326d0ea3d0facf49a6dad39dc2d9 17.219865061000 887098 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": 468400, "vin": [ { "gen": { "height": 468390 } } ], "vout": [ { "amount": 17219865061, "target": { "key": "009fed5a7048027ec1f2cfebe647fe9bf9ad326d0ea3d0facf49a6dad39dc2d9" } } ], "extra": [ 1, 74, 83, 166, 208, 153, 194, 233, 8, 93, 194, 99, 246, 215, 95, 189, 133, 74, 7, 241, 165, 195, 149, 214, 233, 73, 39, 1, 38, 234, 88, 166, 13, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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