Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88eaf1e074bff6c11f570435ce982e4f81fa8161ffd12cdbc59bac44430209ef

Tx prefix hash: 02b12768be22b9452fdccabd03ab6c7ba86dbd036d4373caddae5b593bb6bbd8
Tx public key: abc1197580b4c069b4e508dc1b93f9d3f66cbbc14f8bf8614148a4d958eef071
Timestamp: 1737421887 Timestamp [UCT]: 2025-01-21 01:11:27 Age [y:d:h:m:s]: 00:304:13:30:11
Block: 1201801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215212 RingCT/type: yes/0
Extra: 01abc1197580b4c069b4e508dc1b93f9d3f66cbbc14f8bf8614148a4d958eef07102110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 889a3742399cd9bbecf3da8e89a03426bb1191bed4489f46ac4bd8a5a637f89d 0.600000000000 1688458 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": 1201811, "vin": [ { "gen": { "height": 1201801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "889a3742399cd9bbecf3da8e89a03426bb1191bed4489f46ac4bd8a5a637f89d" } } ], "extra": [ 1, 171, 193, 25, 117, 128, 180, 192, 105, 180, 229, 8, 220, 27, 147, 249, 211, 246, 108, 187, 193, 79, 139, 248, 97, 65, 72, 164, 217, 88, 238, 240, 113, 2, 17, 0, 0, 0, 11, 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