Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d769ada81c5445ce6861e439a4acd5a912cb947da36dfd016c809329a978928d

Tx prefix hash: 9289b38eab6a840ca5d94fb7d52de6e693de35d8eccbef267f2c329606d79f15
Tx public key: 3359a4ce4cad09d4ea4eea4a342a15688b9dcbeadd10398beac27cca27b49a5d
Timestamp: 1711758358 Timestamp [UCT]: 2024-03-30 00:25:58 Age [y:d:h:m:s]: 01:047:23:06:35
Block: 989247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295246 RingCT/type: yes/0
Extra: 013359a4ce4cad09d4ea4eea4a342a15688b9dcbeadd10398beac27cca27b49a5d02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 871da73801496feab17dc52dce6e0f38501a9fd5391a983b8c51ee57aae45246 0.600000000000 1449542 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": 989257, "vin": [ { "gen": { "height": 989247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "871da73801496feab17dc52dce6e0f38501a9fd5391a983b8c51ee57aae45246" } } ], "extra": [ 1, 51, 89, 164, 206, 76, 173, 9, 212, 234, 78, 234, 74, 52, 42, 21, 104, 139, 157, 203, 234, 221, 16, 57, 139, 234, 194, 124, 202, 39, 180, 154, 93, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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