Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 727817c38bd733c30046ea4fd1ae7ba12eb74d819896cd97d32e80b52b595183

Tx prefix hash: 34a6b9a53c1afed84e0ac1379ff5284e6c59606a6bd3d2ed5ceb461431e7f072
Tx public key: 34b1fa4eb41f958485d86741c6aa6406dc253f44c14b013b57d01c33108f3cef
Timestamp: 1700469841 Timestamp [UCT]: 2023-11-20 08:44:01 Age [y:d:h:m:s]: 01:142:14:15:21
Block: 895642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363082 RingCT/type: yes/0
Extra: 0134b1fa4eb41f958485d86741c6aa6406dc253f44c14b013b57d01c33108f3cef02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.661250853000 dcy

stealth address amount amount idx
00: b5c0a87611c280a6373c2f12e9c6823f1eefdfbb2cec740a4f5317bcf3ca1861 0.661250853000 1351883 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": 895652, "vin": [ { "gen": { "height": 895642 } } ], "vout": [ { "amount": 661250853, "target": { "key": "b5c0a87611c280a6373c2f12e9c6823f1eefdfbb2cec740a4f5317bcf3ca1861" } } ], "extra": [ 1, 52, 177, 250, 78, 180, 31, 149, 132, 133, 216, 103, 65, 198, 170, 100, 6, 220, 37, 63, 68, 193, 75, 1, 59, 87, 208, 28, 51, 16, 143, 60, 239, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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