Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4b0aa6452b319153874d1ce10751b0f3694528b0a4698a577b0886afedc6902

Tx prefix hash: 2f1c9002f282ea0c976a58a70ffa028fe13639b37f8788bdc17045b0e81fd528
Tx public key: 6f11904206ecf9fc075d308d18f94ab5368540bb2ce73d4042106e2a8d1d8757
Timestamp: 1673297685 Timestamp [UCT]: 2023-01-09 20:54:45 Age [y:d:h:m:s]: 02:109:17:37:46
Block: 671227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600137 RingCT/type: yes/0
Extra: 016f11904206ecf9fc075d308d18f94ab5368540bb2ce73d4042106e2a8d1d875702110000000152542ceb000000000000000000

1 output(s) for total of 3.663922382000 dcy

stealth address amount amount idx
00: c8773f3a9184f347df0b8839c65a0a8284debae3b91180df8c94d80308b79d92 3.663922382000 1112686 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": 671237, "vin": [ { "gen": { "height": 671227 } } ], "vout": [ { "amount": 3663922382, "target": { "key": "c8773f3a9184f347df0b8839c65a0a8284debae3b91180df8c94d80308b79d92" } } ], "extra": [ 1, 111, 17, 144, 66, 6, 236, 249, 252, 7, 93, 48, 141, 24, 249, 74, 181, 54, 133, 64, 187, 44, 231, 61, 64, 66, 16, 110, 42, 141, 29, 135, 87, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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