Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50f6bebd54d1f831dde4b1f87b31c0e60a836c33a78e73e1adf650495a2af1b

Tx prefix hash: b1b7f39de5dc4cbd4d6f178258ea1ae034a6421a73e41503a413a8a6898ad751
Tx public key: 47111db10b54e82d4a1fbd143f27b9e051845fa1f4443daed81bd9cde9f09d1e
Timestamp: 1622348831 Timestamp [UCT]: 2021-05-30 04:27:11 Age [y:d:h:m:s]: 03:288:05:39:10
Block: 269032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 969300 RingCT/type: yes/0
Extra: 0147111db10b54e82d4a1fbd143f27b9e051845fa1f4443daed81bd9cde9f09d1e02110000001007964887000000000000000000

1 output(s) for total of 78.814348630000 dcy

stealth address amount amount idx
00: f70e3b9fdc755738f401ad34a04cd99e271de514b4772adb650be326ff5b4e65 78.814348630000 564818 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": 269042, "vin": [ { "gen": { "height": 269032 } } ], "vout": [ { "amount": 78814348630, "target": { "key": "f70e3b9fdc755738f401ad34a04cd99e271de514b4772adb650be326ff5b4e65" } } ], "extra": [ 1, 71, 17, 29, 177, 11, 84, 232, 45, 74, 31, 189, 20, 63, 39, 185, 224, 81, 132, 95, 161, 244, 68, 61, 174, 216, 27, 217, 205, 233, 240, 157, 30, 2, 17, 0, 0, 0, 16, 7, 150, 72, 135, 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