Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f173eb26d007e73af5a390b87ab54c7df6b6820e1a3b4cf005760ca7b7be2935

Tx prefix hash: 348bff3e7b3b84a7ea078aaaccecdf56e95a07a4d28ab8bf95136d13c071c8fb
Tx public key: 5490cfe49f5353ee2daee55d898c09bb1b70da6a39150760f1672c081a4bffab
Timestamp: 1718541603 Timestamp [UCT]: 2024-06-16 12:40:03 Age [y:d:h:m:s]: 00:220:05:26:36
Block: 1045479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157541 RingCT/type: yes/0
Extra: 015490cfe49f5353ee2daee55d898c09bb1b70da6a39150760f1672c081a4bffab02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bca49cd1de580aa57b9fc54bc700fe5d41ec96fffa56656e1b57fd6b3a2a1caf 0.600000000000 1515062 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": 1045489, "vin": [ { "gen": { "height": 1045479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bca49cd1de580aa57b9fc54bc700fe5d41ec96fffa56656e1b57fd6b3a2a1caf" } } ], "extra": [ 1, 84, 144, 207, 228, 159, 83, 83, 238, 45, 174, 229, 93, 137, 140, 9, 187, 27, 112, 218, 106, 57, 21, 7, 96, 241, 103, 44, 8, 26, 75, 255, 171, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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