Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce71f66fe318ef7ebc118e2736dbdc4474465270f3e6bff262901eff92906537

Tx prefix hash: bf84fb0bdc2c6c9c3fb8add7424685ed93d7eabba4d2242b68bec4e5d6911bd3
Tx public key: 66c7c01e9192f623664c445782cc7e91850e8eff993987d15b1028c2d79735b9
Timestamp: 1689597617 Timestamp [UCT]: 2023-07-17 12:40:17 Age [y:d:h:m:s]: 01:185:19:24:30
Block: 805769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394133 RingCT/type: yes/0
Extra: 0166c7c01e9192f623664c445782cc7e91850e8eff993987d15b1028c2d79735b902110000000333af99f4000000000000000000

1 output(s) for total of 1.312662063000 dcy

stealth address amount amount idx
00: 2e2e4f090dc7e8ef83cd82d6de5325e5958ca3dd40e9621971e7e98d90f994ee 1.312662063000 1257044 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": 805779, "vin": [ { "gen": { "height": 805769 } } ], "vout": [ { "amount": 1312662063, "target": { "key": "2e2e4f090dc7e8ef83cd82d6de5325e5958ca3dd40e9621971e7e98d90f994ee" } } ], "extra": [ 1, 102, 199, 192, 30, 145, 146, 246, 35, 102, 76, 68, 87, 130, 204, 126, 145, 133, 14, 142, 255, 153, 57, 135, 209, 91, 16, 40, 194, 215, 151, 53, 185, 2, 17, 0, 0, 0, 3, 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