Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 537af945ff95181443223ecc4a4a0ffdd4b8fbf4d4f9a747415f5d7e11bc7c47

Tx prefix hash: 1ac4e5e3287df600513ab8d6d986d27269ccc0761945eb9c48a693cd84ba2ae9
Tx public key: 06bc9032b2606a3bb6eab5e4ce7ae74056f9cc3b4e4174f40a75c8cab5aa7268
Timestamp: 1713522995 Timestamp [UCT]: 2024-04-19 10:36:35 Age [y:d:h:m:s]: 01:038:06:30:28
Block: 1003857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288320 RingCT/type: yes/0
Extra: 0106bc9032b2606a3bb6eab5e4ce7ae74056f9cc3b4e4174f40a75c8cab5aa726802110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac9bfe11058e3e2670a1fd5be7ddaff1ebc06f33d67c50e3e29338cea97c0a98 0.600000000000 1464403 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": 1003867, "vin": [ { "gen": { "height": 1003857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac9bfe11058e3e2670a1fd5be7ddaff1ebc06f33d67c50e3e29338cea97c0a98" } } ], "extra": [ 1, 6, 188, 144, 50, 178, 96, 106, 59, 182, 234, 181, 228, 206, 122, 231, 64, 86, 249, 204, 59, 78, 65, 116, 244, 10, 117, 200, 202, 181, 170, 114, 104, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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