Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7dde94eefa6d9cef61213a22420760dca517f7430ac3e1412aaea2f39923f16

Tx prefix hash: 64da691a2241b1a4307eb5c67b1ed858c118704abe7e5c35df7f46e9fca55102
Tx public key: a306e4742d67c5ca07b32c5195c06ba8264d2ec57d504f1d0f764a04f56905cd
Timestamp: 1702604317 Timestamp [UCT]: 2023-12-15 01:38:37 Age [y:d:h:m:s]: 01:131:13:37:14
Block: 913329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355185 RingCT/type: yes/0
Extra: 01a306e4742d67c5ca07b32c5195c06ba8264d2ec57d504f1d0f764a04f56905cd02110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d3cd631d7d796c92dcc05b45691058ac1bb46428a5ece53ae9324bafbc029d2 0.600000000000 1370597 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": 913339, "vin": [ { "gen": { "height": 913329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d3cd631d7d796c92dcc05b45691058ac1bb46428a5ece53ae9324bafbc029d2" } } ], "extra": [ 1, 163, 6, 228, 116, 45, 103, 197, 202, 7, 179, 44, 81, 149, 192, 107, 168, 38, 77, 46, 197, 125, 80, 79, 29, 15, 118, 74, 4, 245, 105, 5, 205, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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