Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a56f19c693da58ee588a44356ef53718206d8146ef51c2a34f2490aa27364c7

Tx prefix hash: bec56c23e32293c65d322f668f8a8512ca2f79653d2972c79f3d474ad677d5c0
Tx public key: 9db761bc265deed6e97f4b9b213f2d2db2943854c1eeef6bb63d0784b429d9ec
Timestamp: 1682798091 Timestamp [UCT]: 2023-04-29 19:54:51 Age [y:d:h:m:s]: 01:354:04:57:37
Block: 749378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514401 RingCT/type: yes/0
Extra: 019db761bc265deed6e97f4b9b213f2d2db2943854c1eeef6bb63d0784b429d9ec021100000001b3164c24000000000000000000

1 output(s) for total of 2.018435473000 dcy

stealth address amount amount idx
00: 0b5479dedcce2a106db229c8d7e4164b90f781704141c3665ee6b61e5ce85c93 2.018435473000 1197335 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": 749388, "vin": [ { "gen": { "height": 749378 } } ], "vout": [ { "amount": 2018435473, "target": { "key": "0b5479dedcce2a106db229c8d7e4164b90f781704141c3665ee6b61e5ce85c93" } } ], "extra": [ 1, 157, 183, 97, 188, 38, 93, 238, 214, 233, 127, 75, 155, 33, 63, 45, 45, 178, 148, 56, 84, 193, 238, 239, 107, 182, 61, 7, 132, 180, 41, 217, 236, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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