Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4751d952258c2bbaef728dcfa809ed9e4886020eb55cf7bd9d31da39a46a3f01

Tx prefix hash: 443d6c34df0ec21e130b7f16f86d2b513f4d5ec7e623d7be8eb5f8ceb1318361
Tx public key: 7a5c4ca1736c81a568dfbf782f674e0c8cffb9afb0e8fbb89d9c75aa62a91380
Timestamp: 1681662440 Timestamp [UCT]: 2023-04-16 16:27:20 Age [y:d:h:m:s]: 01:360:15:07:39
Block: 739955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519034 RingCT/type: yes/0
Extra: 017a5c4ca1736c81a568dfbf782f674e0c8cffb9afb0e8fbb89d9c75aa62a9138002110000000133af99f4000000000000000000

1 output(s) for total of 2.168813126000 dcy

stealth address amount amount idx
00: fff1b2d530423607beb16fef628b40dea6b7f1df02b19613c544f65663e0b772 2.168813126000 1186834 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": 739965, "vin": [ { "gen": { "height": 739955 } } ], "vout": [ { "amount": 2168813126, "target": { "key": "fff1b2d530423607beb16fef628b40dea6b7f1df02b19613c544f65663e0b772" } } ], "extra": [ 1, 122, 92, 76, 161, 115, 108, 129, 165, 104, 223, 191, 120, 47, 103, 78, 12, 140, 255, 185, 175, 176, 232, 251, 184, 157, 156, 117, 170, 98, 169, 19, 128, 2, 17, 0, 0, 0, 1, 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