Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e13e9b81b9c5a87e8f490b196d94d6ff75ef7faf24813b88022718ec4d0efc0f

Tx prefix hash: be05b121bfbbd60209937631c60283c4f4c7ddbe7e20c03b50e3b7d57e1fd698
Tx public key: b4af52acda30e8d3d5a303e3051101b296ad86148e95bd335c23e8ea036884f2
Timestamp: 1737593675 Timestamp [UCT]: 2025-01-23 00:54:35 Age [y:d:h:m:s]: 00:146:01:02:49
Block: 1203219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104118 RingCT/type: yes/0
Extra: 01b4af52acda30e8d3d5a303e3051101b296ad86148e95bd335c23e8ea036884f2021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5a15141c89a79dd56595be46baefeb94ae351a645c7ef4ff27b742d9c8ef634 0.600000000000 1689892 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": 1203229, "vin": [ { "gen": { "height": 1203219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5a15141c89a79dd56595be46baefeb94ae351a645c7ef4ff27b742d9c8ef634" } } ], "extra": [ 1, 180, 175, 82, 172, 218, 48, 232, 211, 213, 163, 3, 227, 5, 17, 1, 178, 150, 173, 134, 20, 142, 149, 189, 51, 92, 35, 232, 234, 3, 104, 132, 242, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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