Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3555818b050d43f9488f621938d49fffd3b6e6b5a08fce7f6cfa1b06be89cab1

Tx prefix hash: f098abe628b15e4451ac9babfb2cadc36d576175717afbe953803c254ae4b0d8
Tx public key: ce36f49e3c4be74d6848205eaa0649a060c005994f7c9005aa2a1a79b1f0430d
Timestamp: 1737868771 Timestamp [UCT]: 2025-01-26 05:19:31 Age [y:d:h:m:s]: 00:146:00:45:02
Block: 1205487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104071 RingCT/type: yes/0
Extra: 01ce36f49e3c4be74d6848205eaa0649a060c005994f7c9005aa2a1a79b1f0430d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2524e637c336cdbbe97ebaabbb490cb473a449f09f8097107c0969277e119b85 0.600000000000 1692184 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": 1205497, "vin": [ { "gen": { "height": 1205487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2524e637c336cdbbe97ebaabbb490cb473a449f09f8097107c0969277e119b85" } } ], "extra": [ 1, 206, 54, 244, 158, 60, 75, 231, 77, 104, 72, 32, 94, 170, 6, 73, 160, 96, 192, 5, 153, 79, 124, 144, 5, 170, 42, 26, 121, 177, 240, 67, 13, 2, 17, 0, 0, 0, 4, 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