Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7396293dee31d731cd4b5633d1f8bba4ce41b88816cd778cf0e5b4d0729fe22a

Tx prefix hash: e4b8c12ebde00b29f877e3fc58f51ef1c5ca425dfdd8577401ba5f297440c50a
Tx public key: 03b4e3cb25ac626aa029f5187a5385976db0c34f6d54ce8ceca43f97d93b52ad
Timestamp: 1699056155 Timestamp [UCT]: 2023-11-04 00:02:35 Age [y:d:h:m:s]: 01:146:11:24:55
Block: 884129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365676 RingCT/type: yes/0
Extra: 0103b4e3cb25ac626aa029f5187a5385976db0c34f6d54ce8ceca43f97d93b52ad02110000000433af99f4000000000000000000

1 output(s) for total of 0.721960788000 dcy

stealth address amount amount idx
00: b91868d894ef38d45b77274ac1ab4b0042321a3e6c88f0af89015c13a7d67657 0.721960788000 1339862 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": 884139, "vin": [ { "gen": { "height": 884129 } } ], "vout": [ { "amount": 721960788, "target": { "key": "b91868d894ef38d45b77274ac1ab4b0042321a3e6c88f0af89015c13a7d67657" } } ], "extra": [ 1, 3, 180, 227, 203, 37, 172, 98, 106, 160, 41, 245, 24, 122, 83, 133, 151, 109, 176, 195, 79, 109, 84, 206, 140, 236, 164, 63, 151, 217, 59, 82, 173, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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