Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae3183a941c65c95b085041ea8207d435eccd87298bca85ce9a5b2ee02734799

Tx prefix hash: 4bc404eae1408b38eab307525948060a0cace43f9cdfc22676df7eaf0c537ad9
Tx public key: 87036aa8b2bc36bde0ce63b6749f4ee0e725183a8f40d6ce5db8d11d29c8debf
Timestamp: 1745508597 Timestamp [UCT]: 2025-04-24 15:29:57 Age [y:d:h:m:s]: 00:021:06:36:41
Block: 1268518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15216 RingCT/type: yes/0
Extra: 0187036aa8b2bc36bde0ce63b6749f4ee0e725183a8f40d6ce5db8d11d29c8debf02110000000a6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa1496f443e486e156710d137e1d436362dbff37b54028f979ed244a7baf85e7 0.600000000000 1755747 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": 1268528, "vin": [ { "gen": { "height": 1268518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa1496f443e486e156710d137e1d436362dbff37b54028f979ed244a7baf85e7" } } ], "extra": [ 1, 135, 3, 106, 168, 178, 188, 54, 189, 224, 206, 99, 182, 116, 159, 78, 224, 231, 37, 24, 58, 143, 64, 214, 206, 93, 184, 209, 29, 41, 200, 222, 191, 2, 17, 0, 0, 0, 10, 108, 152, 170, 61, 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