Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee5df575901268cd731172dcaeeefab29db9f8bcae48994fcf1e7634f8d1e971

Tx prefix hash: 95f6ad7c62a7230c5b4ac76ff90a27feb6661e7f419a2939e961b513e337a52e
Tx public key: 2399e9a77cbd7c2d83d6c9aa6fdacb50a7384e80187d3faa9ef4d3398c79c916
Timestamp: 1704501228 Timestamp [UCT]: 2024-01-06 00:33:48 Age [y:d:h:m:s]: 01:112:12:34:16
Block: 929041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341563 RingCT/type: yes/0
Extra: 012399e9a77cbd7c2d83d6c9aa6fdacb50a7384e80187d3faa9ef4d3398c79c91602110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9aacf79f63f7264b50fea1e479cf5e1ebe1e86d71bbeea37227e4b019edd729b 0.600000000000 1386909 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": 929051, "vin": [ { "gen": { "height": 929041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9aacf79f63f7264b50fea1e479cf5e1ebe1e86d71bbeea37227e4b019edd729b" } } ], "extra": [ 1, 35, 153, 233, 167, 124, 189, 124, 45, 131, 214, 201, 170, 111, 218, 203, 80, 167, 56, 78, 128, 24, 125, 63, 170, 158, 244, 211, 57, 140, 121, 201, 22, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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