Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 907e073cbac6c83bfa1e0be62f81e1cb54733d7a12ff3102552f726935b21888

Tx prefix hash: 18b4a4f01555f191e11d03a874e2de97f8fdfc6b34c04729cd0b02747753d0dd
Tx public key: ede5f06994089e9f08c3892402974f471e2993b0784af361878c5b3fd433b757
Timestamp: 1724841502 Timestamp [UCT]: 2024-08-28 10:38:22 Age [y:d:h:m:s]: 00:233:08:19:43
Block: 1097692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166643 RingCT/type: yes/0
Extra: 01ede5f06994089e9f08c3892402974f471e2993b0784af361878c5b3fd433b757021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e05d8bf0374a857cc7dfbc299ea525e0c3992b5e3f0ecf027449f3734eae39d 0.600000000000 1573145 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": 1097702, "vin": [ { "gen": { "height": 1097692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e05d8bf0374a857cc7dfbc299ea525e0c3992b5e3f0ecf027449f3734eae39d" } } ], "extra": [ 1, 237, 229, 240, 105, 148, 8, 158, 159, 8, 195, 137, 36, 2, 151, 79, 71, 30, 41, 147, 176, 120, 74, 243, 97, 135, 140, 91, 63, 212, 51, 183, 87, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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