Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0b54d3ae7f84a7d6d769557e4dd82f0a27b2a0360585b5258c5f613e477cf2a

Tx prefix hash: c156710bde79de9aec7c323621b3f16af0141592ff329a6b521d9a376a2e4316
Tx public key: 18a2d2f7620a8851cd49e6e9489d5bf28671b01b1559f8f745d5a1def15e4e5d
Timestamp: 1707782022 Timestamp [UCT]: 2024-02-12 23:53:42 Age [y:d:h:m:s]: 01:088:03:25:26
Block: 956255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324067 RingCT/type: yes/0
Extra: 0118a2d2f7620a8851cd49e6e9489d5bf28671b01b1559f8f745d5a1def15e4e5d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72f486e99823e11729110fd3fe3eb1f1916f1fcd8bb0073e5ba93e10036e0a4c 0.600000000000 1415559 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": 956265, "vin": [ { "gen": { "height": 956255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72f486e99823e11729110fd3fe3eb1f1916f1fcd8bb0073e5ba93e10036e0a4c" } } ], "extra": [ 1, 24, 162, 210, 247, 98, 10, 136, 81, 205, 73, 230, 233, 72, 157, 91, 242, 134, 113, 176, 27, 21, 89, 248, 247, 69, 213, 161, 222, 241, 94, 78, 93, 2, 17, 0, 0, 0, 3, 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