Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e2478b0c989a8e5a829ef4a78352e20873d64c40ef5cda6afcc7283f87c70e4

Tx prefix hash: 886829e3830606f4a3dea3669be3d978a05083ac311ebc45fc95cd80dd248439
Tx public key: 2c20b360a47197586372e3d2c567f29e101de858b4aa0c5e47f8faacc0c0437f
Timestamp: 1675791278 Timestamp [UCT]: 2023-02-07 17:34:38 Age [y:d:h:m:s]: 02:036:08:28:11
Block: 691929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547604 RingCT/type: yes/0
Extra: 012c20b360a47197586372e3d2c567f29e101de858b4aa0c5e47f8faacc0c0437f021100000003faf35c9c000000000000000000

1 output(s) for total of 3.128613498000 dcy

stealth address amount amount idx
00: 3314bea5779b3fa0ee1700c0a15d386dc086ae4a0fa13b689da581d83db95aa1 3.128613498000 1134719 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": 691939, "vin": [ { "gen": { "height": 691929 } } ], "vout": [ { "amount": 3128613498, "target": { "key": "3314bea5779b3fa0ee1700c0a15d386dc086ae4a0fa13b689da581d83db95aa1" } } ], "extra": [ 1, 44, 32, 179, 96, 164, 113, 151, 88, 99, 114, 227, 210, 197, 103, 242, 158, 16, 29, 232, 88, 180, 170, 12, 94, 71, 248, 250, 172, 192, 192, 67, 127, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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