Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca1ed0bd1dc83427daea8ed73abc7b4fb3c6ecf14f56c216dfea57198a97e29b

Tx prefix hash: 055fd7f278bd4821d56e197a520800475f7c68610c5b359d313956aba7c52441
Tx public key: 645754444434f847f665a8d29a4e3c2d423718ca89a8f78b04baac3f5b492f18
Timestamp: 1693829667 Timestamp [UCT]: 2023-09-04 12:14:27 Age [y:d:h:m:s]: 01:251:23:58:15
Block: 840766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441245 RingCT/type: yes/0
Extra: 01645754444434f847f665a8d29a4e3c2d423718ca89a8f78b04baac3f5b492f1802110000000236a45730000000000000000000

1 output(s) for total of 1.005063019000 dcy

stealth address amount amount idx
00: 1da33ea32f7584a6d3ead20add77efd5436aee980e16d141e1106de60114f30e 1.005063019000 1293732 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": 840776, "vin": [ { "gen": { "height": 840766 } } ], "vout": [ { "amount": 1005063019, "target": { "key": "1da33ea32f7584a6d3ead20add77efd5436aee980e16d141e1106de60114f30e" } } ], "extra": [ 1, 100, 87, 84, 68, 68, 52, 248, 71, 246, 101, 168, 210, 154, 78, 60, 45, 66, 55, 24, 202, 137, 168, 247, 139, 4, 186, 172, 63, 91, 73, 47, 24, 2, 17, 0, 0, 0, 2, 54, 164, 87, 48, 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