Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c57396fcba054faedab740ed661ef8ae530413bc4ef1e3fe876d59d4c4ae94

Tx prefix hash: 9fd08c6c1e1a2410a6cbbe6320e629bad32b4750352179a3463072ac83dc7af2
Tx public key: a45089ed99d2fb155e0920f8a3d7099206b12832c60c8f5930870712c19c70a8
Timestamp: 1740389439 Timestamp [UCT]: 2025-02-24 09:30:39 Age [y:d:h:m:s]: 00:259:12:03:43
Block: 1226127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183224 RingCT/type: yes/0
Extra: 01a45089ed99d2fb155e0920f8a3d7099206b12832c60c8f5930870712c19c70a8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 318bfc4cc16dc78e82ccb7ec3915273c7a1c754ca73306b8f1fc9d5ae22456c5 0.600000000000 1712998 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": 1226137, "vin": [ { "gen": { "height": 1226127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "318bfc4cc16dc78e82ccb7ec3915273c7a1c754ca73306b8f1fc9d5ae22456c5" } } ], "extra": [ 1, 164, 80, 137, 237, 153, 210, 251, 21, 94, 9, 32, 248, 163, 215, 9, 146, 6, 177, 40, 50, 198, 12, 143, 89, 48, 135, 7, 18, 193, 156, 112, 168, 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