Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0da4d61963252f23d2b1bc176f2cc7dd1d6060d3b44cab373541c5d4dbf9fc42

Tx prefix hash: cfd3cf708aa4589631719d129a04f548740b56f0177911928c683378940ae75c
Tx public key: 184a5e4c84011f2adb3d95439c7da2fd3e333d72f18ab61dd62d2df542c07473
Timestamp: 1665842586 Timestamp [UCT]: 2022-10-15 14:03:06 Age [y:d:h:m:s]: 02:179:01:10:43
Block: 609627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649592 RingCT/type: yes/0
Extra: 01184a5e4c84011f2adb3d95439c7da2fd3e333d72f18ab61dd62d2df542c07473021100000002faf35c9c000000000000000000

1 output(s) for total of 5.862093302000 dcy

stealth address amount amount idx
00: b509b0eb9e1d4ec22eaa50fa5a4a0c05ae09ab9f77c58033dce3ef0a0e22e741 5.862093302000 1046475 of 0

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": 609637, "vin": [ { "gen": { "height": 609627 } } ], "vout": [ { "amount": 5862093302, "target": { "key": "b509b0eb9e1d4ec22eaa50fa5a4a0c05ae09ab9f77c58033dce3ef0a0e22e741" } } ], "extra": [ 1, 24, 74, 94, 76, 132, 1, 31, 42, 219, 61, 149, 67, 156, 125, 162, 253, 62, 51, 61, 114, 241, 138, 182, 29, 214, 45, 45, 245, 66, 192, 116, 115, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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