Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04e36cb7e3d07e7ff9da65eeb4613c7c70dd967cd2f475b864e422f2d173b937

Tx prefix hash: f4b66ea8b2ce19e7291a792d056776c4a6356400c7db07864fdfe1519dffe81e
Tx public key: eafe9e1d7e3ab93ac3aac43308a52c931823b787286a4a52f5b0498d83094470
Timestamp: 1729497415 Timestamp [UCT]: 2024-10-21 07:56:55 Age [y:d:h:m:s]: 00:093:20:22:22
Block: 1136250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67074 RingCT/type: yes/0
Extra: 01eafe9e1d7e3ab93ac3aac43308a52c931823b787286a4a52f5b0498d83094470021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3100364b0821fbbb1e7c83decc74e44a675b14e50eb0133f589c9e7d1190a177 0.600000000000 1619595 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": 1136260, "vin": [ { "gen": { "height": 1136250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3100364b0821fbbb1e7c83decc74e44a675b14e50eb0133f589c9e7d1190a177" } } ], "extra": [ 1, 234, 254, 158, 29, 126, 58, 185, 58, 195, 170, 196, 51, 8, 165, 44, 147, 24, 35, 183, 135, 40, 106, 74, 82, 245, 176, 73, 141, 131, 9, 68, 112, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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