Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98f2c4fde5dd90ff49bd3680e81affc6b85db023d5c3be41f093957601150cf3

Tx prefix hash: 626ee91dcf5b7d5cc34a0d2cb89293cb80e9a4bfce64612e215c5c15fb8687dc
Tx public key: e0b535e2dbad3b13e7546644e0161e6328066b130d414e2aef98a009146a1615
Timestamp: 1738170216 Timestamp [UCT]: 2025-01-29 17:03:36 Age [y:d:h:m:s]: 00:141:02:30:41
Block: 1207783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100791 RingCT/type: yes/0
Extra: 01e0b535e2dbad3b13e7546644e0161e6328066b130d414e2aef98a009146a1615021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4beb6e4c1fc79aef565828e94ace06880f137c701b19f77ec9a52f7c0a3a4429 0.600000000000 1694508 of 15

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": 1207793, "vin": [ { "gen": { "height": 1207783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4beb6e4c1fc79aef565828e94ace06880f137c701b19f77ec9a52f7c0a3a4429" } } ], "extra": [ 1, 224, 181, 53, 226, 219, 173, 59, 19, 231, 84, 102, 68, 224, 22, 30, 99, 40, 6, 107, 19, 13, 65, 78, 42, 239, 152, 160, 9, 20, 106, 22, 21, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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