Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a6cd6316fb4910b958d5ba17619c9fc441d9089d3958d4562ad3d4c72efea21

Tx prefix hash: 8b3c3e74b90be524d4e1bb6fb9d0d3333fd464b575b171c95d9520a6a7c6987f
Tx public key: cd9df59d4b1f1ce4f51ae6fc290dc701bb1b73480c3da1753e160b5171f35db8
Timestamp: 1705447972 Timestamp [UCT]: 2024-01-16 23:32:52 Age [y:d:h:m:s]: 01:308:17:54:29
Block: 936883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479495 RingCT/type: yes/0
Extra: 01cd9df59d4b1f1ce4f51ae6fc290dc701bb1b73480c3da1753e160b5171f35db80211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 779b1e4ed409dc6b0b2a68bd130b5e7c1f6d6705c78153396f971577cf2fa8fe 0.600000000000 1394925 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": 936893, "vin": [ { "gen": { "height": 936883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "779b1e4ed409dc6b0b2a68bd130b5e7c1f6d6705c78153396f971577cf2fa8fe" } } ], "extra": [ 1, 205, 157, 245, 157, 75, 31, 28, 228, 245, 26, 230, 252, 41, 13, 199, 1, 187, 27, 115, 72, 12, 61, 161, 117, 62, 22, 11, 81, 113, 243, 93, 184, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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