Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90141d82c2d16d0b5bc7552f237199855a0b5ac7823197e9d20550cecee955f1

Tx prefix hash: 401cefa66ce71e862103610fa1c6d9ab7fdbb718304b0f8aeb2c843988ec27a0
Tx public key: dbebae2167df2b22800db41fc2234ef4e93e17da7c6f0f78b16f7f2635a6dfcf
Timestamp: 1698659281 Timestamp [UCT]: 2023-10-30 09:48:01 Age [y:d:h:m:s]: 01:197:07:46:22
Block: 880849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402050 RingCT/type: yes/0
Extra: 01dbebae2167df2b22800db41fc2234ef4e93e17da7c6f0f78b16f7f2635a6dfcf0211000000024b8f5122000000000000000000

1 output(s) for total of 0.740255455000 dcy

stealth address amount amount idx
00: 680d75888e011a83771049550566f71cfb96ae84bb6346d62bd59683a17bafd9 0.740255455000 1336419 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": 880859, "vin": [ { "gen": { "height": 880849 } } ], "vout": [ { "amount": 740255455, "target": { "key": "680d75888e011a83771049550566f71cfb96ae84bb6346d62bd59683a17bafd9" } } ], "extra": [ 1, 219, 235, 174, 33, 103, 223, 43, 34, 128, 13, 180, 31, 194, 35, 78, 244, 233, 62, 23, 218, 124, 111, 15, 120, 177, 111, 127, 38, 53, 166, 223, 207, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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