Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28a803162c47d30cec79a1f44df20ee873c227265a746bd5ad89c513ffb2c98a

Tx prefix hash: 167b70467f5e90ada40dcbe3a8daf72ae231edb2ee7cfc460e9a235a15e31da4
Tx public key: 4696e95239ade9c21d23efbb04ef498fd51a0f69e7d600eb61cf8ade434101c9
Timestamp: 1699512712 Timestamp [UCT]: 2023-11-09 06:51:52 Age [y:d:h:m:s]: 01:129:19:36:11
Block: 887710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353966 RingCT/type: yes/0
Extra: 014696e95239ade9c21d23efbb04ef498fd51a0f69e7d600eb61cf8ade434101c902110000000133af99f4000000000000000000

1 output(s) for total of 0.702503133000 dcy

stealth address amount amount idx
00: 170b60d2234de71d53760604bc52e5e45afdd8cc8b8388fa0e1cc436c9e2f2a5 0.702503133000 1343605 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": 887720, "vin": [ { "gen": { "height": 887710 } } ], "vout": [ { "amount": 702503133, "target": { "key": "170b60d2234de71d53760604bc52e5e45afdd8cc8b8388fa0e1cc436c9e2f2a5" } } ], "extra": [ 1, 70, 150, 233, 82, 57, 173, 233, 194, 29, 35, 239, 187, 4, 239, 73, 143, 213, 26, 15, 105, 231, 214, 0, 235, 97, 207, 138, 222, 67, 65, 1, 201, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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