Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26bcb33a3797e92c064a09f5c0a1922b393203dbaf4438143a4831033a29c620

Tx prefix hash: 7936b6a994132ff2aff96f5bdbe110d900be3cb094ba57d86d1fb350c68d87a5
Tx public key: 6b122a9539509f2618f12969f8261ae2aa8c1310bda620bf5d39b8812e8b9083
Timestamp: 1704512230 Timestamp [UCT]: 2024-01-06 03:37:10 Age [y:d:h:m:s]: 01:305:18:38:24
Block: 929125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477380 RingCT/type: yes/0
Extra: 016b122a9539509f2618f12969f8261ae2aa8c1310bda620bf5d39b8812e8b90830211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aacf3213cba9d63f3a7ccbea2a20a35da0cb691ca79e2cbcb532c59af2a848b4 0.600000000000 1386993 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": 929135, "vin": [ { "gen": { "height": 929125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aacf3213cba9d63f3a7ccbea2a20a35da0cb691ca79e2cbcb532c59af2a848b4" } } ], "extra": [ 1, 107, 18, 42, 149, 57, 80, 159, 38, 24, 241, 41, 105, 248, 38, 26, 226, 170, 140, 19, 16, 189, 166, 32, 191, 93, 57, 184, 129, 46, 139, 144, 131, 2, 17, 0, 0, 0, 2, 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