Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 653c42cb993c11d907d053144fcf39726d197cde6859c0752a2d89b6143d37dd

Tx prefix hash: b1aa7087cb9266d2bf04f4d667cb128beb9ab2e18168d39161236d2b1c52ddc0
Tx public key: ef8fdbda4ec57a5be4440764e7dc72a0416163b2f9a207cde0b4762f75146d41
Timestamp: 1712158717 Timestamp [UCT]: 2024-04-03 15:38:37 Age [y:d:h:m:s]: 00:265:10:09:25
Block: 992529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190034 RingCT/type: yes/0
Extra: 01ef8fdbda4ec57a5be4440764e7dc72a0416163b2f9a207cde0b4762f75146d4102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28de950ed7276571d1320d35deba0e1064af8b931a0960c54a31dc18bdef8a2a 0.600000000000 1452875 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": 992539, "vin": [ { "gen": { "height": 992529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28de950ed7276571d1320d35deba0e1064af8b931a0960c54a31dc18bdef8a2a" } } ], "extra": [ 1, 239, 143, 219, 218, 78, 197, 122, 91, 228, 68, 7, 100, 231, 220, 114, 160, 65, 97, 99, 178, 249, 162, 7, 205, 224, 180, 118, 47, 117, 20, 109, 65, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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