Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a25cf922808a3eae1e13276ed822e8b6ce37ee5fad9ec900d99a3e4e92b04b1

Tx prefix hash: 48fc355752740725a9baee36a729f8116698ca49f275cf5300ce64cfe54f79e8
Tx public key: bf1a44089dfbb9450c1cac79e596966bf5bd22f039559f8f013b4362eefe6b52
Timestamp: 1722660441 Timestamp [UCT]: 2024-08-03 04:47:21 Age [y:d:h:m:s]: 00:295:18:33:43
Block: 1079615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211329 RingCT/type: yes/0
Extra: 01bf1a44089dfbb9450c1cac79e596966bf5bd22f039559f8f013b4362eefe6b52021100000004daef6b5b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a61367364162d08a897773a9e77b3a9d00c23ed91fb6b4a55a24466a1659192 0.600000000000 1552644 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": 1079625, "vin": [ { "gen": { "height": 1079615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a61367364162d08a897773a9e77b3a9d00c23ed91fb6b4a55a24466a1659192" } } ], "extra": [ 1, 191, 26, 68, 8, 157, 251, 185, 69, 12, 28, 172, 121, 229, 150, 150, 107, 245, 189, 34, 240, 57, 85, 159, 143, 1, 59, 67, 98, 238, 254, 107, 82, 2, 17, 0, 0, 0, 4, 218, 239, 107, 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