Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f802c70338cfe1fbe5b9f7f2cca0774c6bc4262a338fb9bb779196622394f2

Tx prefix hash: 664ca831e12c69459892892d0650c684d0ce5edb2f5ff6754b2c9e53a0c587eb
Tx public key: a23e82b51f064adf99b15b7a2b40021baf084039e3f30ce0053010ef3ef30eae
Timestamp: 1729843619 Timestamp [UCT]: 2024-10-25 08:06:59 Age [y:d:h:m:s]: 00:068:07:48:32
Block: 1139122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48851 RingCT/type: yes/0
Extra: 01a23e82b51f064adf99b15b7a2b40021baf084039e3f30ce0053010ef3ef30eae0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 780a5299c0fdceb6428feaf47fd0152d6d2f3dc45c9eadcaa063baf384115443 0.600000000000 1622885 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": 1139132, "vin": [ { "gen": { "height": 1139122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "780a5299c0fdceb6428feaf47fd0152d6d2f3dc45c9eadcaa063baf384115443" } } ], "extra": [ 1, 162, 62, 130, 181, 31, 6, 74, 223, 153, 177, 91, 122, 43, 64, 2, 27, 175, 8, 64, 57, 227, 243, 12, 224, 5, 48, 16, 239, 62, 243, 14, 174, 2, 17, 0, 0, 0, 4, 31, 10, 83, 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