Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 137044ca40ebad9d63dd976f10b1682bd57fc09a3443d4e26e4b0a765c481b87

Tx prefix hash: dff5de1d432f69e5bdd70df910c8ff7595030c2dc924682fdd618145007b77e4
Tx public key: 5db2f6406ab3da75b7a9c5adeba76b4d420ae6a7b0e4f05652d74e3e9df7b418
Timestamp: 1673588007 Timestamp [UCT]: 2023-01-13 05:33:27 Age [y:d:h:m:s]: 02:119:18:15:29
Block: 673645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607279 RingCT/type: yes/0
Extra: 015db2f6406ab3da75b7a9c5adeba76b4d420ae6a7b0e4f05652d74e3e9df7b4180211000000038b7b6602000000000000000000

1 output(s) for total of 3.596950188000 dcy

stealth address amount amount idx
00: fc934e10ebaac6f77a23304ae526228398602b4ab80bbd7a59cb94e438be56d1 3.596950188000 1115260 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": 673655, "vin": [ { "gen": { "height": 673645 } } ], "vout": [ { "amount": 3596950188, "target": { "key": "fc934e10ebaac6f77a23304ae526228398602b4ab80bbd7a59cb94e438be56d1" } } ], "extra": [ 1, 93, 178, 246, 64, 106, 179, 218, 117, 183, 169, 197, 173, 235, 167, 107, 77, 66, 10, 230, 167, 176, 228, 240, 86, 82, 215, 78, 62, 157, 247, 180, 24, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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