Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44075a9a09cee2fa6850ca6dec3783c1bbae9523c0a353347022bd411cf0f389

Tx prefix hash: 747ffabfb332a6e013ee9191275015aa52a2d1c6199c87ff409280cc6eeeb3ce
Tx public key: e7c3b74d478127b1ff840e45e8470fde154c6d10ff4ae447f7d43d8090c8f6d6
Timestamp: 1699427479 Timestamp [UCT]: 2023-11-08 07:11:19 Age [y:d:h:m:s]: 01:362:00:38:04
Block: 887002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517646 RingCT/type: yes/0
Extra: 01e7c3b74d478127b1ff840e45e8470fde154c6d10ff4ae447f7d43d8090c8f6d6021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.706308064000 dcy

stealth address amount amount idx
00: f8d23200cef04c01b4b6455fd3cdda3785c46f3d48cf7a5089c2e8c955c820f7 0.706308064000 1342853 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": 887012, "vin": [ { "gen": { "height": 887002 } } ], "vout": [ { "amount": 706308064, "target": { "key": "f8d23200cef04c01b4b6455fd3cdda3785c46f3d48cf7a5089c2e8c955c820f7" } } ], "extra": [ 1, 231, 195, 183, 77, 71, 129, 39, 177, 255, 132, 14, 69, 232, 71, 15, 222, 21, 76, 109, 16, 255, 74, 228, 71, 247, 212, 61, 128, 144, 200, 246, 214, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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