Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ecb44b122e6e7a3eebeee8f8e1c201c7f2ce960de5688e45626f7e62ca1c550

Tx prefix hash: bc2183b1855125eed7608165046c3e15354ca14a481a1e3943b9e105852efc6b
Tx public key: c56f27dc117c285dd28408f65db8c900cfb4bc8c6d1a26371f02f9d5b941d10f
Timestamp: 1721607991 Timestamp [UCT]: 2024-07-22 00:26:31 Age [y:d:h:m:s]: 00:254:05:28:42
Block: 1070872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181616 RingCT/type: yes/0
Extra: 01c56f27dc117c285dd28408f65db8c900cfb4bc8c6d1a26371f02f9d5b941d10f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d1e19a57f3909c5916309c420c4d62c408230cc1722f37f024b892ebd2cd83c 0.600000000000 1542887 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": 1070882, "vin": [ { "gen": { "height": 1070872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d1e19a57f3909c5916309c420c4d62c408230cc1722f37f024b892ebd2cd83c" } } ], "extra": [ 1, 197, 111, 39, 220, 17, 124, 40, 93, 210, 132, 8, 246, 93, 184, 201, 0, 207, 180, 188, 140, 109, 26, 38, 55, 31, 2, 249, 213, 185, 65, 209, 15, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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