Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f1403a281a41eda8e46d85a8d28aa1f44620b4cbcc3defd3c137399957c38e

Tx prefix hash: a1df0b6d938081d931f030c39296164cbb41722056ccfed91d53e7ba366ae915
Tx public key: 29a84d22fd4ff5ca0d42d4396c153bf109d0bb4501e93c1170f1736d504f7949
Timestamp: 1728290154 Timestamp [UCT]: 2024-10-07 08:35:54 Age [y:d:h:m:s]: 00:052:00:14:37
Block: 1126287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37158 RingCT/type: yes/0
Extra: 0129a84d22fd4ff5ca0d42d4396c153bf109d0bb4501e93c1170f1736d504f794902110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0bbf1b896977f1d62db51b4f8d4f146802c0b14329c1e754f7d4e708181ebbb 0.600000000000 1609076 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": 1126297, "vin": [ { "gen": { "height": 1126287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0bbf1b896977f1d62db51b4f8d4f146802c0b14329c1e754f7d4e708181ebbb" } } ], "extra": [ 1, 41, 168, 77, 34, 253, 79, 245, 202, 13, 66, 212, 57, 108, 21, 59, 241, 9, 208, 187, 69, 1, 233, 60, 17, 112, 241, 115, 109, 80, 79, 121, 73, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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