Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45b11b45576e0a0310474c70ef502f58ac7e1b572f6ffa70f257250bfe70661b

Tx prefix hash: d6b45b27158785e67b0ea3e67d14a084031143b0e5a24b031b239cc1480b1d6e
Tx public key: aef70e33fc3d22dcc791160c0c9550172a8fd89ad50453ac36ac22164d81279b
Timestamp: 1728842768 Timestamp [UCT]: 2024-10-13 18:06:08 Age [y:d:h:m:s]: 00:172:07:43:24
Block: 1130861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122934 RingCT/type: yes/0
Extra: 01aef70e33fc3d22dcc791160c0c9550172a8fd89ad50453ac36ac22164d81279b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46777cba715a3f5e9cb3dbe18b3719dc99d7b30e55731f313f4c5f1cf1f5c9a8 0.600000000000 1613742 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": 1130871, "vin": [ { "gen": { "height": 1130861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46777cba715a3f5e9cb3dbe18b3719dc99d7b30e55731f313f4c5f1cf1f5c9a8" } } ], "extra": [ 1, 174, 247, 14, 51, 252, 61, 34, 220, 199, 145, 22, 12, 12, 149, 80, 23, 42, 143, 216, 154, 213, 4, 83, 172, 54, 172, 34, 22, 77, 129, 39, 155, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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