Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8debefd8491c8d3c1a24f1e20447a3107680d9ba36beee6af49f77be50862444

Tx prefix hash: 88bd64f965266779ec416ff97b57af0e3c3a3456172cd8d5491e70bbf93db399
Tx public key: 8ce978b558061fdc42cf98013985b4fdb08ff95749c555fe089520cde4d20df1
Timestamp: 1574456899 Timestamp [UCT]: 2019-11-22 21:08:19 Age [y:d:h:m:s]: 05:041:19:00:52
Block: 14762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1173217 RingCT/type: yes/0
Extra: 018ce978b558061fdc42cf98013985b4fdb08ff95749c555fe089520cde4d20df1021100000001b63f0b49000000000000000000

1 output(s) for total of 548.388388478000 dcy

stealth address amount amount idx
00: 2be9c21ade0c42439b5afb1df7c13c3d3448e4f3c7051f6b829861fa74d1b5aa 548.388388478000 19080 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": 14772, "vin": [ { "gen": { "height": 14762 } } ], "vout": [ { "amount": 548388388478, "target": { "key": "2be9c21ade0c42439b5afb1df7c13c3d3448e4f3c7051f6b829861fa74d1b5aa" } } ], "extra": [ 1, 140, 233, 120, 181, 88, 6, 31, 220, 66, 207, 152, 1, 57, 133, 180, 253, 176, 143, 249, 87, 73, 197, 85, 254, 8, 149, 32, 205, 228, 210, 13, 241, 2, 17, 0, 0, 0, 1, 182, 63, 11, 73, 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