Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8b2613d262f0e9ba0295217d8d5b9a7126aa71368bcdea6b4cd2e0f3dd5eb29

Tx prefix hash: f9cae1672b9736d1de2b86ea4e4782587a5993258be1c46bc24239ed7c3661fa
Tx public key: cfaac2a1ed2413260b74cd331d8ad40c032eeefc5854b5ea4626d940d4f8c34c
Timestamp: 1713258174 Timestamp [UCT]: 2024-04-16 09:02:54 Age [y:d:h:m:s]: 01:201:17:24:49
Block: 1001644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402835 RingCT/type: yes/0
Extra: 01cfaac2a1ed2413260b74cd331d8ad40c032eeefc5854b5ea4626d940d4f8c34c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61feab5d4c2735b50bc83b69d4b2fd717d7e7a7b65931b8dc7a385a5b660155c 0.600000000000 1462152 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": 1001654, "vin": [ { "gen": { "height": 1001644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61feab5d4c2735b50bc83b69d4b2fd717d7e7a7b65931b8dc7a385a5b660155c" } } ], "extra": [ 1, 207, 170, 194, 161, 237, 36, 19, 38, 11, 116, 205, 51, 29, 138, 212, 12, 3, 46, 238, 252, 88, 84, 181, 234, 70, 38, 217, 64, 212, 248, 195, 76, 2, 17, 0, 0, 0, 1, 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