Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43f41fd4ed0f32d9f2854566a0b9eda6c80918f388e4a11d727cb8f3e1c1c447

Tx prefix hash: 25caff5598ee3cff1ac3af2dada152519a5e7c10abfe05947f80697a882634c0
Tx public key: 07588a01e1f192567fb3687031b2300cc97027827880390c9760c4a0c3d26805
Timestamp: 1702524030 Timestamp [UCT]: 2023-12-14 03:20:30 Age [y:d:h:m:s]: 01:132:21:00:38
Block: 912674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356117 RingCT/type: yes/0
Extra: 0107588a01e1f192567fb3687031b2300cc97027827880390c9760c4a0c3d2680502110000000733af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ab1f8d6ee1393c9e2f1f985194e8f797bbffc04e197fef2151cb0836861c42c 0.600000000000 1369906 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": 912684, "vin": [ { "gen": { "height": 912674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ab1f8d6ee1393c9e2f1f985194e8f797bbffc04e197fef2151cb0836861c42c" } } ], "extra": [ 1, 7, 88, 138, 1, 225, 241, 146, 86, 127, 179, 104, 112, 49, 178, 48, 12, 201, 112, 39, 130, 120, 128, 57, 12, 151, 96, 196, 160, 195, 210, 104, 5, 2, 17, 0, 0, 0, 7, 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