Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c280d7d16a1dec1801d46a8fa84f54e8fccfd0e9a546ecf3136e1b13f4af07a2

Tx prefix hash: f65f38ae2af1a6f2ca2732165496b05b98771cff58f0afeb76e614c031926816
Tx public key: 17cc2fd714919632b871aff031ebab72c7e19f2c0962fce3db8a8de101200841
Timestamp: 1717554163 Timestamp [UCT]: 2024-06-05 02:22:43 Age [y:d:h:m:s]: 01:154:12:51:38
Block: 1037285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368999 RingCT/type: yes/0
Extra: 0117cc2fd714919632b871aff031ebab72c7e19f2c0962fce3db8a8de1012008410211000000020bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49d8e0573b99bcc7448c1db71e0d4cde8b95905dc29c4833fae8c8337892e1ae 0.600000000000 1505816 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": 1037295, "vin": [ { "gen": { "height": 1037285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49d8e0573b99bcc7448c1db71e0d4cde8b95905dc29c4833fae8c8337892e1ae" } } ], "extra": [ 1, 23, 204, 47, 215, 20, 145, 150, 50, 184, 113, 175, 240, 49, 235, 171, 114, 199, 225, 159, 44, 9, 98, 252, 227, 219, 138, 141, 225, 1, 32, 8, 65, 2, 17, 0, 0, 0, 2, 11, 186, 22, 215, 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