Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a3ff7f2c93043624accc8a4139edaf3af5f2ed7322b1df6039c34ef5a342767

Tx prefix hash: 551149880f17cce7722371a2b2f0ed3a3ff40330fa3ef060e359862a84348aad
Tx public key: 3dc664a34068c64b77054d90210bda32e9dd0e4a2c9e38a9cfa13f2cd0ee2984
Timestamp: 1706340185 Timestamp [UCT]: 2024-01-27 07:23:05 Age [y:d:h:m:s]: 01:097:15:19:32
Block: 944280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330888 RingCT/type: yes/0
Extra: 013dc664a34068c64b77054d90210bda32e9dd0e4a2c9e38a9cfa13f2cd0ee29840211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9853bb4dcb843f527a4442e0498e074f9e954df07e54ed631b5b917e9b3aa803 0.600000000000 1402516 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": 944290, "vin": [ { "gen": { "height": 944280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9853bb4dcb843f527a4442e0498e074f9e954df07e54ed631b5b917e9b3aa803" } } ], "extra": [ 1, 61, 198, 100, 163, 64, 104, 198, 75, 119, 5, 77, 144, 33, 11, 218, 50, 233, 221, 14, 74, 44, 158, 56, 169, 207, 161, 63, 44, 208, 238, 41, 132, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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